View HT45B0K_4854295.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

rev 1.00 march 22, 2010 1 HT45B0K spi to usb bridge features glueless slave spi interface to holtek ' s mcu usb (universal serial bus) 1.1 full-speed module ? 6 endpoints (endpoint 0 included) ? fifo: 8, 8, 8, 64, 8, 64 for ep0~ep5 respectively operating voltage: v dd = 3.3v~5.5v 6mhz/12mhz (clki) external clock input for usb pll clock suspend mode with low suspend current remote wake-up function usb multiple interrupt generation sources: ? access of the corresponding usb fifo from the usb host ? usb suspend signal from the usb host ? usb resume signal from the usb host ? usb reset signal from the usb host cmos external clock input, clki, with frequency 6mhz/12mhz for the usb pll clock 16-pin nsop package general description this device is a companion chip for microcontrollers to provide usb connectivity with the usb host. six usb endpoints are supported with 8/8/8/64/8/64-byte fifo for endpoint 0~5 respectively. an external interrupt output to the host mcu is used for inetrrupt-driven operation. however, the host mcu may also poll the status register to obtain the latest status if the interrupt is not used. the possible applications include low-cost data links for computers/peripherals, portable and battery operated devices/instruments, factory automation and process control. block diagram
! "
# " $ % % &
rev 1.00 march 22, 2010 2 HT45B0K spi to usb bridge pin assignment

' ( ' ) ' ' ' * ' ' ' + , ' * ) ( - pin description pin name i/o descriptions sdi i serial i/o data input sdi is high impedance when = high sdo o serial i/o data output. sdo is high impedance when = high sck i serial i/o clock input sck is high impedance when = high i serial i/o chip select input, low active connected to internal pull-high resistor. clki i external clock input o interrupt output - cmos output structure connected to the external interrupt input of mcu a usb related interrupt will generate a low pulse signal on this line v33o 3.3v regulator output udp i/o usbd+ line usb function is controlled by software control register. udn i/o usbd- line usb function is controlled by software control register. vdd positive power supply vss negative power supply, ground nc no connection absolute maximum ratings supply voltage....................................................................................................v ss ? 0.3v to v ss +6.0v input voltage.......................................................................................................v ss ? 0.3v to v dd +0.3v storage temperature................................................................................................. ? 50c to +150c operating temperature................................................................................................. ? 40c to +85c i oh total.......................................................................................................................... ........... ? 10ma i ol total......................................................................................................................... ..............15ma total power dissipation........................................................................................................ ......10mw these are stress ratings only. stresses exceeding the range speci ed under ?absolute maximum ratings? may cause substantial damage to the device. functional operation of this device at other conditions beyond those listed in the speci cation is not implied and prolonged exposure to extreme conditions may affect device reliability. note :
rev 1.00 march 22, 2010 3 HT45B0K spi to usb bridge d.c. characteristics symbol parameter test conditions min. typ. max. unit v dd conditions v dd operating voltage D f clki =6mhz or 12mhz 3.3 D 5.5 v i dd operating current (spi enabled, usb transceiver and 3.3v regulator on) 3.3v f clki =6mhz, sck= f clki /4 D 4.0 6.0 ma 5.0v D 6.5 10 ma 3.3v f clki =12mhz, sck= f clki /4 D 4.0 7.0 ma 5.0v D 7.0 10 ma i sus suspend current (spi enabled, usb suspend and 3.3v regulator on) D output no load, susp2=1 (bit 4 in ucc) D 400 500 a i stb standby current (spi disabled, usb disabled and 3.3v regulator off) D output no load D 0.1 1 a v il1 input low voltage for i/o pins DD 0 D 0.3 v dd v v ih1 input high voltage for i/o pins DD 0.7 v dd D v dd v v il2 input low voltage for clki DD 0 D 0.3 v dd v v ih2 input high voltage for clki DD 0.7 v dd D v dd v i ol i/o pins sink current 3.3v v o =0.1 v dd 4.0 12 D ma 5.0v 10 25 D ma i oh i/o pins source current 3.3v v o =0.9 v dd -4.0 -5.0 D ma 5.0v -5.0 -10 D ma r ph pull-high resistance for only 3.3v D 15 45 75 k 5v 10 30 50 k
rev 1.00 march 22, 2010 4 HT45B0K spi to usb bridge a.c. characteristics symbol parameter test conditions min. typ. max. unit v dd conditions r por v dd slew rate for por DD 0.0034 DD v/ms f clki system clock (external clock input) 3.3v~ 5.0v D D 6 D mhz D 12 D mhz t cp sck period (t ch + cl ) 3.3v D 62.5 DD ns 5.0v D 50.0 DD ns t ch sck high time 3.3v D 28 DD ns 5.0v D 22 DD ns t cl sck low time 3.3v D 28 DD ns 5.0v D 22 DD ns t csw high pulse width 3.3v D 500 DD ns 5.0v D 400 DD ns t css to sck setup time DD 100 DD ns t csh to sck hold time DD 0 DD ns t sds sdi to sck setup time DD 100 DD ns t sdh sdi to sck hold time DD 0 DD ns t r spi output rise time DDD 10 D ns t f spi output fall time DDD 10 D ns t w spi data output delay time DD 0 DD ns
rev 1.00 march 22, 2010 5 HT45B0K spi to usb bridge functional description the mcu communicates with the usb module via an internal spi interface. the spi interface on this device is comprised of four signals: (spi chip select), sck (spi clock), sdi (serial data input) and sdo (serial data output). the spi master, which is the mcu, asserts by pulling it low to start the data transaction cycle. when the rst 8 bits of data are transmitted, should not return to a high level. instead, must remain at a low level until the whole 16-bit data transaction is completed. if is de-asserted, that is returned to a high level, before the 16- bit data transaction is completed, all data bits will be discarded by the usb module spi slave. spi interface both read and write operations are conducted along the spi common interface with the following format: write type format: 8-bit command input + 8-bit data input read type format: 8-bit command input + 8-bit data output to initiate a data transaction, the mcu master spi needs to pull to a low level rst and then also pull sck low. the input data bit on sdi should be stable before the next sck rising edge, as the device will latch the sdi status on the next sck rising edge. regarding the sdo line, the output data bit will be updated on the sck falling edge. the master needs to obtain the line status before the next sck falling edge. there are 16 bits of data transmitted and/or received by the spi interface for each transaction. each transaction consists of a command phase and a data phase. when is high, the spi interface is disabled and sdo will be set to a high impedance state. after a complete transaction has been implemented, which requires 16 sck clock cycles, the master needs to set to a high level in preparation for the next data transaction. for write operations, the device will begin to execute the command only after it receives a 16-bit serial data sequence and when the has been set high again by the master. for read operations, the device will begin to execute the command only after it receives an 8-bit read command after which it will be ready to output data. if necessary, the master can de-assert the pin to abort the transaction at any time which will cause any data transactions to be abandoned. spi timing there are 2 types of commands: read register write register commands and registers command type bit.7 bit.6 bit.5 bit.4 bit.3 bit.2 bit.1 bit.0 read register 0 x x a4 a3 a2 a1 a0 write register 1 x x a4 a3 a2 a1 a0 there are 17 registers available to control the usb module which are addressed by 5 address bits a4~ a0 of read /write register commands. command/address format
rev 1.00 march 22, 2010 6 HT45B0K spi to usb bridge reading type format:8-bit command input + 8-bit data input sdo sck sdi scs a7 a6 a5 a4 a3 a2 a1 a0 don t care t w writing type format:8-bit command input + 8-bit data input sdo sck sdi scs a7 a6 a5 a4 a3 a2 a1 a0 d7 d7 d6 d5 d4 d3 d2 d1 d0 d6 d5 d4 d3 d2 d1 d0
rev 1.00 march 22, 2010 7 HT45B0K spi to usb bridge usb module to communicate with an external usb host, the internal usb module has the external pins known as udp and udn along with the 3.3v regulator output v33o. all data transmissions and receptions between mcu and usb module including usb commands are conducted along the interconnected spi interface. the usb module has 6 endpoints and 160 bytes fifo for the endpoints respectively. a serial interface engine (sie) decodes the incoming usb data stream and transfers it to the correct endpoint buffer memory (fifo). the usb function control is implemented using a series of registers accessed by the mcu using its spi master serial interface. a series of status registers provide the user with the usb data transfer situation as well as any error conditions. the usb contains its own independent interrupt which can be used to indicate when the usb fifos are accessed by the host device or a change of the usb operating conditions including the usb suspend mode, resume event or usb reset occurs. there are both read and write commands for accessing the usb module. for reading and writing to registers, both command and address information is contained within a single byte. a series of registers which are addressed by 5 address bits a4~a0 are available to control the usb module for read/write registers commands. the format for reading and writing commands is shown in the following table. command type bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 read registers 0 x x a4 a3 a2 a1 a0 write registers 1 x x a4 a3 a2 a1 a0 note: ?x? here stands for ?don?t care?. usb accessing commands there are several registers associated with the usb function. some of the registers control the overall function of the usb module as well as the interrupts, while some of the registers contain the status bits which indicate the usb data transfer situations and error condition. also there are fifos for the usb endpoints to store the data received from or to be transmitted to the usb host. the usb module has 6 endpoints (ep0~ep5) with different fifo size for each one. the fifo size is 8 bytes for ep0~ep2 and ep4 which support ?interrupt transfer?, while the fifo size for ep3 and ep5 is 64 bytes which can support ?bulk transfer?. usb status and control registers
rev 1.00 march 22, 2010 8 HT45B0K spi to usb bridge address name por state bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 00h usc --00 0000 DD pll v33c resume urst rmwk susp 01h usr --00 0000 DD ep5if ep4if ep3if ep2if ep1if ep0if 02h ucc -0-0 0000 D sysclk D susp2 usbcken eps2 eps1 eps0 03h awr 0000 0000 uad6 uad5 uad4 uad3 uad2 uad1 uad0 wken 04h stall --11 1110 DD stl5 stl4 stl3 stl2 stl1 stl0 05h sies 0100 0000 nmi eot crcf nak in out err aset 06h misc 0x1- -000 len0 ready setcmd DD clear tx request 07h setio --11 1110 DD setio5 setio4 setio3 setio2 setio1 d atatg 08h uic --00 0000 DD eu5i eu4i eu3i eu2i eu1i eu0i 09h unused ---- ---- reserved 0ah pipe 0-00 000- suspc D ep5e ep4e ep3e ep2e ep1e D 0bh swrst ---- ---0 DD D D D DD reset 0ch~0fh unused ---- ---- reserved 10h fifo0 xxxx xxxx data for endpoint 0 11h fifo1 xxxx xxxx data for endpoint 1 12h fifo2 xxxx xxxx data for endpoint 2 13h fifo3 xxxx xxxx data for endpoint 3 14h fifo4 xxxx xxxx data for endpoint 4 15h fifo5 xxxx xxxx data for endpoint 5 16h~1fh unused ---- ---- reserved usb register summary usc register the usc register contains the status bits for usb suspend, resume and reset indications. it also contains the bits used to control the remote wake-up, v33o output and pll functions. further explanation on each bit is given below: usc register bit 76543210 name DD pll v33c resume urst rmwk susp r/w DD r/w r/w r r r/w r por DD 000000 bit 7~6 unimplemented, read as ?0?. bit 5 pll: pll enable control 0: turn on the pll 1: turn off the pll bit 4 v33c: v33o output enable control 0: turn off the v33o output 1: turn on the v33o output bit 3 resume: usb resume indication ag 0: usb device does not receive the resume signal or has left the suspend mode. 1: usb device receives the resume signal and is going to leave the suspend mode. when the usb device receives the resume signal, this bit is set to 1 by sie. this bit will appear for about 20ms, waiting for the mcu to detect it. when the resume is set by sie, an interrupt will be generated to wake up the mcu. in order to detect the suspend state, mcu should set the usbcken bit to 1 and clear the pll and suspc bits to 0 to enable the sie and phy functions. the resume bit will be cleared when the susp bit
rev 1.00 march 22, 2010 9 HT45B0K spi to usb bridge is set to 0. when the mcu detects the suspend mode susp, the resume signal resume which causes mcu to wake up should be remembered and taken into consideration. bit 2 urst: usb reset indication ag 0: no usb reset event occurred. 1: usb reset event has occurred. the usb bit is set and cleared by usb sie. when the urst bit is set to 1, it indicates that a usb reset event has occurred and a usb interrupt will be initiated. bit 1 rmwk: usb remote wake-up command 0: disable usb remote wake-up command 1: initiate usb remote wake-up command the rmwk is set to 1 by mcu to force the usb host leaving the suspend mode. set rmwk bit to 1 to initiate the remote walk-up command. when the rmwk bit is set to 1, a 2 s delay for clearing this bit to 0 is necessary to ensure that the rmwk command is accepted by the sie. bit 0 susp: usb suspend indication ag 0: usb leaves the suspend mode. 1: usb enters the suspend mode. this bit is read only and set to 1 by sie to indicate that the usb bus enters the suspend mode. the usb interrupt is also generated when the susp bit is asserted. usr register the usr (usb endpoint interrupt status register) register is consisted of the endpoint request ags (ep0if~ep5if) used to indicate which endpoint is accessed. when an endpoint is accessed, the related endpoint request ag will be set to 1 by sie and a usb interrupt will be generated if the control bits related to the usb interrupt are enabled and the stack in the host mcu is not full. when the active endpoint request ag is serviced, the endpoint request ag has to be cleared to 0 by application program. usr register bit 76543210 name DD ep5if ep4if ep3if ep2if ep1if ep0if r/w DD r/w r/w r/w r/w r/w r/w por DD 000000 bit 7~6 unimplemented, read as ?0?. bit 5~0 ep5if~ep0if: endpoint interrupt request ags 0: the corresponding endpoint is not accessed. 1: the corresponding endpoint has been accessed.
rev 1.00 march 22, 2010 10 HT45B0K spi to usb bridge ucc register the ucc register is the system clock control register implemented to select the clock used by the mcu. this register consists of usb clock control bit usbcken, second suspend mode control bit susp2 and system clock selection bit sysclk. this register is also used to select which endpoint fifo is accessed by endpoint fifo selection bits eps2~eps0. further explanation on each of the bits is given below: ucc register bit 7 6 5 4 3 2 1 0 name D sysclk D susp2 usbcken eps2 eps1 eps0 r/w D r/w D r/w r/w r/w r/w r/w por D 0 D 00000 bit 7 unimplemented, read as ?0?. bit 6 sysclk: system clock input selection 0: 12mhz clock is used 1: 6mhz clock is used this bit is used to specify the system clock oscillator frequency used by the mcu. if a 6mhz crystal oscillator or resonator is used, this bit should be set to 1. if a 12mhz crystal oscillator or resonator is used, this bit should be set to 0. bit 5 unimplemented, read as ?0?. bit 4 susp2: suspend mode 2 control 0: optimized setting in suspend mode 1: test setting in suspend mode. the band-gap circuit is turned off. it is strongly recommended that this bit should be set to 0 when the usb interface is in suspend mode. otherwise, the unpredictable results will occur. bit 3 usbcken: usb clock enable control 0: usb clock is disabled 1: usb clock is enabled when the usb device receives the suspend signal sent from the usb host, the usb clock enable control bit usbcken should be set to 0 to reduce the power consumption. bit 2~0 eps2~eps0: endpoint fifo selection 000: endpoint 0 fifo is selected 001: endpoint 1 fifo is selected 010: endpoint 2 fifo is selected 011: endpoint 3 fifo is selected 100: endpoint 4 fifo is selected 101: endpoint 5 fifo is selected 11x: reserved for further expansion and can not be used. the eps2~eps0 bits are used to select which endpoint is to be accessed. if the selected endpoint does not exist, the related functions are not available.
rev 1.00 march 22, 2010 11 HT45B0K spi to usb bridge awr register the awr register contains the usb device address and the remote wake-up function control bit. the initial value of the usb device address is 00h. the address value extracted from the usb command is to be immediately loaded into this register or not depending upon the device address update control bit aset in the sies register. awr register bit 7 6 5 4 3 2 1 0 name uad6 uad5 uad4 uad3 uad2 uad1 uad0 wken r/w r/w r/w r/w r/w r/w r/w r/w r/w por 0 0 0 0 0 0 0 0 bit 7~1 uad6~uad0: usb device address bit 0 wken: usb device remote wake-up function enable control 0: disable usb remote wake-up function 1: enable usb remote wake-up function stall register the stall register shows whether the corresponding endpoint works properly or not. as soon as the endpoint works improperly, the related bit in the stall register has to be set to 1 by application program. the contents of the stall register will be cleared by usb reset signal. stall register bit 7 6 5 4 3 2 1 0 name DD stl5 stl4 stl3 stl2 stl1 stl0 r/w DD r/w r/w r/w r/w r/w r/w por DD 111111 bit 7~6 unimplemented, read as ?0?. bit 5~0 stl5~stl0: usb endpoint stall indication 0: the corresponding usb endpoint is not stalled. 1: the corresponding usb endpoint is stalled. the stl bit is set by users when the related usb endpoint is stalled. these bits are cleared by usb reset signal. for endpoint 0 the stall bit stl0 can also be cleared by setup token event.
rev 1.00 march 22, 2010 12 HT45B0K spi to usb bridge sies register the sies register is used to indicate the present signal state which the sie receives and also control whether the sie changes the device address automatically or not. sies register bit 7 6 5 4 3 2 1 0 name nmi eot crcf nak in out err aset r/w r/w r r/w r r r/w r/w r/w por 0 0 0 0 0 0 0 0 bit 7 nmi: endpoint 0 nak token interrupt mask control 0: endpoint 0 nak token interrupt is not masked. 1: endpoint 0 nak token interrupt is masked. if this bit is set to 1, the interrupt will not occur when the device sends a nak token to the usb host from endpoint 0. otherwise, when this bit is set to 0 and the device endpoint 0 sends a nak token to the usb host, the endpoint 0 nak token interrupt will be generated if the corresponding endpoint interrupt control is enabled. bit 6 eot: end of transaction indication ag 0: usb transaction is in progress. 1: usb transaction has ended. if this bit is zero, it indicates that the usb transaction is in progress. when the level of the eot bit changes from 0 to 1, it means that the usb transaction has ended. bit 5 crcf: error indication ag during transfer 0: no usb transfer error occurs. 1: usb transfer error has occurred. the error conditions include crc, pid and incomplete token errors. the crcf bit is set by hardware and is necessary to be cleared by rmware. bit 4 nak: nak signal indication ag 0: no nak signal is transmitted. 1: nak signal has been transmitted. the nak bit is used to indicate that the sie has transmitted a nak signal to the usb host in response to the usb host in or out token when the endpoint was accessed. bit 3 in: in token indication ag for endpoint 0 0: the received token packet is not in token. 1: the received token packet is in token. the in bit is used to indicate that for the usb endpoint 0 the current received signal from the usb host is in token. bit 2 out: out token indication ag for endpoint 0 0: the received token packet is not out token. 1: the received token packet is out token. the out bit is used to indicate that for the usb endpoint 0 the current received signal from the usb host is out token except for the out zero length token. the rmware clears this bit after the out data has been read. also, this bit will be cleared by sie after the next valid setup token is received. bit 1 err: error indication ag during endpoint 0 fifo is accessed 0: no error occurs during endpoint 0 fifo is accessed.
rev 1.00 march 22, 2010 13 HT45B0K spi to usb bridge 1: error has occurred during endpoint 0 fifo is accessed. the err bit is used to indicate that there are some errors occurred during endpoint 0 fifo is accessed. this bit is set by sie and should be cleared by rmware. bit 0 aset: device address update control 0: device address is updated immediately when the awr register is written. 1: device address is updated after the device in token data has been read (setup stage nished). the aset bit is used to con gure the sie to automatically update the device address with the value stored in the awr register. when this bit is set to 1 by firmware, the sie will update the device address with the value stored in the awr register after the usb host has successfully read the data from the device by in token. otherwise, when this bit is cleared to 0, the sie will update the device address immediately after an address is written to the awr register. misc register the misc register contains the commands to control the desired endpoint fifo action along with the status to show the condition of the desired endpoint fifo. the misc register will be cleared by a usb reset signal. misc register bit 7 6 5 4 3 2 1 0 name len0 ready setcmd DD clear tx request r/w r/w r r/w DD r/w r/w r/w por 0 x 1 DD 00 0 ?x? means unknown. bit 7 len0: zero-length packet indication ag for endpoint 0 0: no operation. 1: a zero-length packet is sent from the usb host. if this bit is set to 1, it indicates that a 0-sized packet is sent from a usb host. this bit should be cleared by the application program or by the next valid setup token. bit 6 ready: endpoint fifo ready indication ag 0: the desired endpoint fifo is not ready. 1: the desired endpoint fifo is ready. this bit is used to indicate whether the desired endpoint fifo is ready to operate or not. bit 5 setcmd: setup command indication ag 0: the data in the endpoint 0 fifo is not setup token. 1: the data in the endpoint 0 fifo is setup token. this bit is used to indicate whether the data in the endpoint 0 fifo is setup token or not. it is set by hardware and cleared by rmware. bit 4~3 unimplemented, read as ?0?. bit 2 clear: clear requested fifo 0: no operation. 1: clear the requested endpoint fifo. this bit is used by mcu to clear the requested fifo, even if the fifo is not ready. if user wants to clear the current requested endpoint fifo, the clear bit should be set to 1 to generate a positive pulse with 2 s pulse width and then clear this bit to zero. bit 1 tx: direction of data transfer between the mcu and the endpoint fifo
rev 1.00 march 22, 2010 14 HT45B0K spi to usb bridge 0: the data transfer from the endpoint fifo to the mcu (mcu read data from the endpoint fifo). 1: the data transfer from the mcu to the endpoint fifo (mcu write data to the endpoint fifo). this bit de nes the direction of data transfer between the mcu and the endpoint fifo. when the tx bit is set to high, this means that the mcu desires to write data to the endpoint fifo. after the mcu write operation has been complete, this bit has to be cleared to zero before terminating fifo request to indicate the end of data transfer. for a mcu read operation, this bit has to be cleared to zero to show that the mcu desires to read data from the endpoint fifo and has to be set to high before terminating fifo request to indicate the end of data transfer after the completion of mcu read operation. bit 0 request: fifo request control 0: no operation. 1: request the desired fifo. this bit is used to request the operation of the desired fifo. after selecting the desired endpoint, the fifo can be requested by setting this bit to high. after completion, this bit has to be cleared to zero. the mcu can communicate with the endpoint fifo by setting the corresponding registers, whose addresses are listed in the following table. after reading the current data, the next data will show after 2 s, used to check the endpoint fifo status and responds to the misc register, if a read/write action is still being implemented. some timing constrains are listed here. by setting the misc register, the mcu can perform reading, writing and clearing actions. there are some examples shown in the following for the endpoint fifo reading, writing and clearing. read or write fifon table (n=0~5) actions misc setting flow and status check whether fifon can be read or not 00h 01h delay 2 s, check 41h (ready) or 01h (not ready) 00h. check whether fifon can be written or not 02h 03h delay 2 s, check 43h (ready) or 03h (not ready) 02h. read fifon sequence 00h 01h delay 2 s, check 41h read* from fifon register and check not ready (01h) 03h 02h. write fifon sequence 02h 03h delay 2 s, check 43h write* to fifon register and check not ready (03h) 01h 00h. read 0-sized packet sequence from fifo0 00h 01h delay 2 s, check 81h clear len0 (01h) 03h 02h. write 0-sized packet sequence to fifon 02h 03h delay 2 s 01h 00h. note *: there are 2 s existing between 2 reading actions or between 2 writing actions. . / 0 /
. / 1 2
3 . / 0 /
. / 1 2
3
rev 1.00 march 22, 2010 15 HT45B0K spi to usb bridge setio register the setio register is used to con gure the endpoint fifo as in pipe or out pipe. setio register bit 7 6 5 4 3 2 1 0 name DD setio5 setio4 setio3 setio2 setio1 d atatg r/w DD r/w r/w r/w r/w r/w r/w por DD 1111 1 0 bit 7~6 unimplemented, read as ?0?. bit 5~1 setio5~setio1: endpoint 5 fifo ~ endpoint fifo1 pipe direction control. 0: the corresponding endpoint fifo is con gured as out pipe. 1: the corresponding endpoint fifo is con gured as in pipe. if the related setio bit is set to 1, the corresponding endpoint fifo is con gured as in pipe for in token operation. otherwise, the corresponding endpoint fifo is con gured as out pipe for out token operation. the purpose of this function is to avoid the usb host from abnormally sending only an in token or out token and disable the related endpoint. bit 0 datatg: data0 toggle bit 0: no operation. 1: data0 will be sent rst. as the usb specification defined, when the usb host sends a ?set configuration? setup token, the data pipe should send the data0 (data toggle) first. therefore, when the usb device receives a ?set con guration? setup token, user needs to set datatg bit to 1 and then clear it to zero after a 2 s delay to generate a positive pulse with 2 s pulse width to make sure that the next data will send a data0 rst. uic register the uic register is used to control the interrupt request for each endpoint. interrupts can be enabled or disabled independently if the corresponding endpoint fifo pipes are enabled. uic register bit 7 6 5 4 3 2 1 0 name DD eu5i eu4i eu3i eu2i eu1i eu0i r/w DD r/w r/w r/w r/w r/w r/w por DD 0000 0 0 bit 7~6 unimplemented, read as ?0?. bit 5~0 eu5i~eu0i: usb endpoint 5 ~ endpoint 0 interrupt control as being accessed. 0: disable the corresponding endpoint interrupt as it is accessed. 1: enable the corresponding endpoint interrupt as it is accessed. if the related endpoint fifo pipe is enabled and the corresponding endpoint interrupt is enabled, the usb interrupt for endpoint access will occur. then a low pulse signal will be generated on line to get the attentions from the host mcu.
rev 1.00 march 22, 2010 16 HT45B0K spi to usb bridge pipe register the pipe register is used to control that the fifo pipe for each endpoint is enabled or disable. the endpoint access interrupt can be controlled independently by con guring the uic register if the corresponding endpoint fifo pipe is enabled. pipe register bit 7 6 5 4 3 2 1 0 name suspc D ep5e ep4e ep3e ep2e ep1e D r/w r/w D r/w r/w r/w r/w r/w D por 0 D 0000 0 D bit 7 suspc: usb phy control in suspend mode 0: the usb phy is enabled. 1: the usb phy is disabled. if the usb enters the suspend mode, user can set suspc bit to 1 to disable the usb phy for low power consumption. when the usb receives the resume signal from the usb host, the suspc bit should be set to 0 to make sure that the usb phy can work normally. bit 6 unimplemented, read as ?0?. bit 5~1 ep5e~ep1e: usb endpoint 5 ~ endpoint 0 fifo pipe enable control. 0: the corresponding endpoint fifo pipe is disabled. 1: the corresponding endpoint fifo pipe is enabled. if the corresponding endpoint fifo pipe is disabled, the read/write operations to the related endpoint fifo pipe are not available. if the corresponding endpoint fifo pipe and the interrupt are both enabled, the related usb endpoint interrupt will be generated as the interrupt trigger events occur. otherwise, if the endpoint fifo pipe or the endpoint interrupt is disabled, the corresponding endpoint interrupt will not be generated. bit 0 unimplemented, read as ?0?. swrst register the swrst register controls the software reset operation of the device. the only one available bit named reset in the swrst register is the device software reset control bit. when this bit is equal to ?0?, the device operates normally. if this bit is equal to ?1?, the whole device will be reset act just like power-on reset. when this situation occurs, all of the device registers and the circuitry relevant to spi interface and usb module will be reset. the registers in this device including the status registers and control registers will keep the por states shown in the above usb registers summary table after the reset condition occurs. swrst register bit 7 6 5 4 3 2 1 0 name D D DDDD D reset r/w D D DDDD D r/w por D D DDDD D 0 bit 7~1 unimplemented, read as ?0?. bit 0 reset: device software reset 0: no action 1: device reset occurs
rev 1.00 march 22, 2010 17 HT45B0K spi to usb bridge fifo0~fifo5 registers the fifo0~fifo5 registers are used for data transactions between the usb device and the usb host. the mcu reads data from or writes data to the fifos via the spi interface to complete data interchange. for ?interrupt transfer? it is supported by fifo0~fifo2 and fifo4, while it is supported by fifo3 and fifo5 for ?bulk transfer?. fifo0~fifo5 registers label type por misc setting flow and status fifo0 r/w xxxx xxxx data pipe for endpoint 0, depth = 8 bytes fifo1 r/w xxxx xxxx data pipe for endpoint 1, depth = 8 bytes fifo2 r/w xxxx xxxx data pipe for endpoint 2, depth = 8 bytes fifo3 r/w xxxx xxxx data pipe for endpoint 3, depth = 64 bytes fifo4 r/w xxxx xxxx data pipe for endpoint 4, depth = 8 bytes fifo5 r/w xxxx xxxx data pipe for endpoint 5, depth = 64 bytes ?x? means unknown.
rev 1.00 march 22, 2010 18 HT45B0K spi to usb bridge usb module suspend mode and wake-up if there is no signal on the usb bus for over 3ms, the devices will go into a suspend mode. the suspend indication bit susp, bit 0 of the usc register, will be set to 1 and a usb interrupt will be generated to indicate that the device should jump to the suspend state to meet the 500 a usb suspend current specification. in order to meet the 500 a suspend current, the firmware should disable the usb clock by clearing the usb clock enable control bit usbcken in the ucc register to 0. also the usb pll and phy circuitry control bits known as pll and suspc should be set to 1 to disable the usb pll and phy function. the suspend current is about 400 a. usb suspend mode when the resume signal is asserted by the usb host, the usb device will be woken up with a usb interrupt generated on the int line and the resume indication bit resume in the usc register will be set. in order to make the device function properly, the application program must set the usbcken bit in the ucc register to 1 and clear the pll and suspc bits in the usc register and pipe register respectively to 0. when the resume signal is de-asserted by the usb host, the usb device actually leaves the suspend mode and the usb host will start to communicate with the usb device. the susp bit will be cleared as well as the resume bit when the usb device really leaves the suspend mode. so when the mcu is detecting the suspend bit, the resume bit should be stored and taken into consideration. the following diagram shows the relationship between the susp and resume bits and int signal. usb host wake-up . / /
suspend and host wake-up as the device has a remote wake-up function, it can wake up the usb host by sending a wake-up pulse by setting the rmwk bit in the usc register to 1 for 2 s and then setting the rmwk bit to 0. once the usb host receives a wake-up signal from the device, it will send a resume signal to the device. the timing is as follows: usb remote wake-up suspend and remote wake-up . / /
. 4 * 5 ) 6 7 # 8 5 9 2 s (min.)
rev 1.00 march 22, 2010 19 HT45B0K spi to usb bridge usb interrupt structure several individual usb conditions can generate a usb interrupt. these conditions are the usb suspended, usb resume, usb reset and usb endpoint fifo access events. when the usb interrupt caused by any of these conditions occurs, a low pulse will be generated on the int line to get the attention of the microcontroller or microprocessor. for the usb endpoint fifo access event, there are the corresponding indication ags to indicate which endpoint fifo is accessed. as the endpoint fifo access ag is set, it will generate a usb interrupt on int line if the associated endpoint fifo pipe and interrupt control are both enabled. the endpoint fifo access flags should be cleared by the application program. as the usb suspended, usb resume or usb reset condition occurs, the corresponding indication ag, known as susp, resume and urst bits, will be set and a usb interrupt will directly generated without any associated interrupt control being enabled. the susp, resume and urst bits are read only and set or cleared by the usb sie. 7 % # " # ! : # . 7 6 # " # ! : # ! . 7 # " # ! : # / % # ; ; # " " 7 7 " # ! : # # . : 7 . # . : 7 + ' + ' # . : 7 / # . : 7
usb interrupt structure
rev 1.00 march 22, 2010 20 HT45B0K spi to usb bridge application circuit mcu connection
7 #
) +
usb connection for 5v application ' + ; # ' * < = + 5 ' ; + 5 ' ;
) + , ' ' ' ' + ( ' * ' ' ( ) ' -
- % ; + 5 ' ; ' 5 ) - % ; usb connection for 3.3v application + 5 ' ; - % ; ' + ;
- ' *
# ' * < = 5 ' + ; 5 - % ; 5 + 5 ' ;
) +
5 + 5 ' ; ' 5 ) + 5 ' ; ( ' ' ( ) , ' ' ' ' + ' * ' -
rev 1.00 march 22, 2010 21 HT45B0K spi to usb bridge package information 16-pin nsop (150mil) outline dimensions ms-012 symbol dimensions in inch min. nom. max. a 0.228 D 0.244 b 0.150 D 0.157 c 0.012 D 0.020 c? 0.386 D 0.394 d DD 0.069 e D 0.050 D f 0.004 D 0.010 g 0.016 D 0.050 h 0.007 D 0.010 0 D 8 ' ( ' , 1 / ; > symbol dimensions in mm min. nom. max. a 5.79 D 6.20 b 3.81 D 3.99 c 0.30 D 0.51 c? 9.80 D 10.01 d DD 1.75 e D 1.27 D f 0.10 D 0.25 g 0.41 D 1.27 h 0.18 D 0.25 0 D 8
rev 1.00 march 22, 2010 22 HT45B0K spi to usb bridge reel dimensions 1
'
* sop 16n (150mil) symbol description dimensions in mm a reel outer diameter 330.01.0 b reel inner diameter 100.01.5 c spindle hole diameter 13.0 +0.5/-0.2 d key slit width 2.00.5 t1 space between flange 16.8 +0.3/-0.2 t2 reel thickness 22.20.2
rev 1.00 march 22, 2010 23 HT45B0K spi to usb bridge carrier tape dimensions ' 4 ' + / ; + + 1 + # % " ? : # % # ' # # $ # # $ 7 # " # # $ # 7 6 # 7 5 . # symbol description dimensions in mm w carrier tape width 16.00.3 p cavity pitch 8.00.1 e perforation position 1.750.1 f cavity to perforation (width direction) 7.50.1 d perforation diameter 1.55 +0.10/-0.00 d1 cavity hole diameter 1.50 +0.25/-0.00 p0 perforation pitch 4.00.1 p1 cavity to perforation (length direction) 2.00.1 a0 cavity length 6.50.1 b0 cavity width 10.30.1 k0 cavity depth 2.10.1 t carrier tape thickness 0.300.05 c cover tape width 13.30.1

▲Up To Search▲

Price & Availability of HT45B0K

	To Download HT45B0K Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .